Skip to content

Conversation

@wilsonrf
Copy link
Contributor

@wilsonrf wilsonrf commented Jun 24, 2025

Resolves #1285
Related #1265

The warn log was introduced in the latest release for a failed function lookup.
If I understood correctly, this is being emitted on every first call to the function when the first lookup happens, which can significantly pollute the logs in production environments.
Since this message seems not to indicate an error or unexpected behaviour, but rather reflects a normal and expected code path, debug can be a more appropriate log level.

This is my first contribution to the project - please feel free to disregard if you believe this change is not aligned with the logging strategy.

Resolves spring-cloud#1285

Signed-off-by: Wilson da Rocha Franca <wilsonrf@gmail.com>
@olegz
Copy link
Contributor

olegz commented Jun 27, 2025

I agree with your assertion, so will merge

@olegz olegz added this to the 5.0 milestone Jun 27, 2025
@olegz olegz closed this in dec0287 Jun 27, 2025
olegz pushed a commit that referenced this pull request Jun 27, 2025
Resolves #1285

Signed-off-by: Wilson da Rocha Franca <wilsonrf@gmail.com>
Resolves #1286
olegz pushed a commit that referenced this pull request Jun 27, 2025
Resolves #1285

Signed-off-by: Wilson da Rocha Franca <wilsonrf@gmail.com>
Resolves #1286
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Change log level to debug for failed function lookup

2 participants